View MBM29LV320BE80TR_1047341.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

ds05-20894-1e fujitsu semiconductor data sheet flash memory cmos 32 m (4 m 8/2 m 16) bit mbm29lv320te 80/90/10 mbm29lv320be 80 / 90 / 10 n description the mbm29lv320te/be is 32 m-bit, 3.0 v-only flash memory organized as 4 m bytes of 8 bits each or 2 m words of 16 bits each. the device is offered in a 48-pin tsop (i) and 63-ball fbga packages. this device is designed to be programmed in-system with the standard system 3.0 v v cc supply. 12.0 v v pp and 5.0 v v cc are not required for write or erase operations. the device can also be reprogrammed in standard eprom programmers. the standard device offers access times 80 ns, 90 ns and 100 ns, allowing operation of high-speed microproces- sors without wait state. to eliminate bus contention the device has separate chip enable(ce ), write enable(we ) and output enable (oe ) controls. (continued) n product line up n packages part no. mbm29lv320te/be 80 90 100 power supply voltage (v) v cc = 3.3 v v cc = 3.0 v max address access time (ns) 80 90 100 max ce access time (ns) 80 90 100 max oe access time (ns) 30 35 35 + 0.3 v - 0.3 v + 0.6 v - 0.3 v 48-pin plastic tsop (i) 48-pin plastic tsop (i) 63-ball plastic fbga (fpt-48p-m19) (fpt-48p-m20) (bga-63p-m01) marking side marking side
mbm29lv320te/be 80/90/10 2 (continued) the device is pin and command set compatible with jedec standard e 2 proms. commands are written to the command register using standard microprocessor write timings. register contents serve as input to an internal state-machine which controls the erase and programming circuitry. write cycles also internally latch addresses and data needed for the programming and erase operations. reading data out of the device is similar to reading from 5.0 v and 12.0 v flash or eprom devices. the device is programmed by executing the program command sequence. this will invoke the embedded program algorithm which is an internal algorithm that automatically times the program pulse widths and verifies proper cell margin. typically, each sector can be programmed and verified in about 0.5 seconds. erase is accomplished by executing the erase command sequence. this will invoke the embedded erase algorithm which is an internal algorithm that automatically preprograms the array if it is not already programmed before executing the erase operation. during erase, the device automatically time the erase pulse widths and verify proper cell margin. a sector is typically erased and verified in 1.0 second. (if already completely preprogrammed.) the device also features a sector erase architecture. the sector mode allows each sector to be erased and reprogrammed without affecting other sectors. the device is erased when shipped from the factory. the device features single 3.0 v power supply operation for both read and write functions. internally generated and regulated voltages are provided for the program and erase operations. a low v cc detector automatically inhibits write operations on the loss of power. the end of program or erase is detected by data polling of dq 7 , by the toggle bit feature on dq 6 , or the ry/by output pin. once the end of a program or erase cycle has been completed, the device internally resets to the read mode. the device also has a hardware reset pin. when this pin is driven low, execution of any embedded program algorithm or embedded erase algorithm is terminated. the internal state machine is then reset to the read mode. the reset pin may be tied to the system reset circuitry. therefore, if a system reset occurs during the embedded program algorithm or embedded erase algorithm, the device is automatically reset to the read mode and will have erroneous data stored in the address locations being programmed or erased. these locations need re-writing after the reset. resetting the device enables the systems microprocessor to read the boot-up firmware from the flash memory. fujitsus flash technology combines years of eprom and e 2 prom experience to produce the highest levels of quality, reliability, and cost effectiveness. the device memory electrically erase the entire chip or all bits within a sector simultaneously via fowler-nordhiem tunneling. the bytes/words are programmed one byte/word at a time using the eprom programming mechanism of hot electron injection.
mbm29lv320te/be 80/90/10 3 n features ? 0.23 m m m m m process technology ? single 3.0 v read, program, and erase minimized system level power requirements ? compatible with jedec-standard commands use the same software commands as e 2 proms ? compatible with jedec-standard world-wide pinouts 48-pin tsop (i) (package suffix : tn - normal bend type, tr - reversed bend type) 63-ball fbga (package suffix : pbt) ? minimum 100,000 program/erase cycles ? high performance 80 ns maximum access time ? sector erase architecture eight 4 k word and sixty-three 32 k word sectors in word mode eight 8 k byte and sixty-three 64 k byte sectors in byte mode any combination of sectors can be concurrently erased. also supports full chip erase. ? boot code sector architecture t = top sector b = bottom sector ? hidden rom (hi-rom) region 256 byte of hi-rom, accessible through a new hi-rom enable command sequence factory serialized and protected to provide a secure electronic serial number (esn) ? wp /acc input pin at v il , allows protection of boot sectors, regardless of sector protection/unprotection status at v ih , allows removal of boot sector protection at v acc , increases program performance ? embedded erase tm * algorithms automatically pre-programs and erases the chip or any sector ? embedded program tm * algorithms automatically writes and verifies data at specified address ? data polling and toggle bit feature for detection of program or erase cycle completion ? ready/busy output (ry/by ) hardware method for detection of program or erase cycle completion ? automatic sleep mode when addresses remain stable, automatically switch themselves to low power mode. ? low v cc write inhibit 2.5 v ? erase suspend/resume suspends the erase operation to allow a read data and/or program in another sector within the same device ? sector group protection hardware method disables any combination of sector groups from program or erase operations ? sector group protection set function by extended sector group protection command ? fast programming function by extended command ? temporary sector group unprotection temporary sector group unprotection via the reset pin. ? in accordance with cfi (c ommon f lash memory i nterface) * : embedded erase tm and embedded program tm are trademarks of advanced micro devices , inc.
mbm29lv320te/be 80/90/10 4 n pin assignments (continued) tsop (i) (fpt-48p-m19) (fpt-48p-m20) a 15 a 14 a 13 a 12 a 11 a 10 a 9 a 8 a 19 a 20 we reset n.c. wp/acc ry/by a 18 a 17 a 7 a 6 a 5 a 4 a 3 a 2 a 1 a 16 byte v ss dq 15 /a -1 dq 7 dq 14 dq 6 dq 13 dq 5 dq 12 dq 4 v cc dq 11 dq 3 dq 10 dq 2 dq 9 dq 1 dq 8 dq 0 oe v ss ce a 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 (marking side) mbm29lv320te/be normal bend a 1 a 2 a 3 a 4 a 5 a 6 a 7 a 17 a 18 ry/by wp/acc n.c. reset we a 20 a 19 a 8 a 9 a 10 a 11 a 12 a 13 a 14 a 15 a 0 ce v ss oe dq 0 dq 8 dq 1 dq 9 dq 2 dq 10 dq 3 dq 11 v cc dq 4 dq 12 dq 5 dq 13 dq 6 dq 14 dq 7 dq 15 /a -1 v ss byte a 16 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 (marking side) mbm29lv320te/be reverse bend
mbm29lv320te/be 80/90/10 5 (continued) fbga (top view) marking side (bga-63p-m01) a8 b8 n.c. n.c. n.c. n.c. a7 b7 c7 d7 e7 f7 g7 h7 byte j7 k7 c6 d6 e6 f6 g6 h6 j6 k6 a 9 a 8 a 10 a 11 dq 7 dq 14 dq 13 dq 6 c5 d5 e5 f5 g5 h5 j5 k5 we reset n.c. a 19 dq 5 dq 12 v cc dq 4 c4 d4 e4 f4 g4 h4 j4 k4 ry/by wp/ acc a 18 a 20 dq 2 dq 10 dq 11 dq 3 c3 d3 e3 f3 g3 h3 j3 k3 a 7 a 17 a 6 a 5 dq 0 dq 8 dq 9 dq 1 c2 d2 e2 f2 g2 h2 j2 k2 l2 m2 a 3 a2 n.c. a1 n.c. b1 n.c. a 4 a 2 a 1 a 0 ce oe v ss l7 l8 m7 a 13 a 12 a 14 a 15 a 16 dq 15 / a -1 v ss n.c. n.c. m8 n.c. n.c. l1 n.c. m1 n.c. n.c. n.c.
mbm29lv320te/be 80/90/10 6 n pin description mbm29lv320 te/be pin configuration table pin function a 20 to a 0 , a -1 address inputs dq 15 to dq 0 data inputs/outputs ce chip enable oe output enable we write enable ry/by ready/busy output reset hardware reset pin/temporary sector group unprotection byte selects 8-bit or 16-bit mode wp /acc hardware write protection/program acceleration n.c. no internal connection v ss device ground v cc device power supply
mbm29lv320te/be 80/90/10 7 n block diagram n logic symbol a -1 v ss v cc we ce a 20 to a 09 oe dq 15 to dq 0 byte reset wp/acc stb stb erase voltage generator ry/by buffer ry/by state control command register program voltage generator input/output buffers data latch chip enable output enable logic low v cc detector timer for program/erase address latch y-decoder x-decoder y-gating cell matrix 21 a 20 to a 0 we ry/by oe ce dq 15 to dq 0 16 or 8 reset a -1 byte wp/acc
mbm29lv320te/be 80/90/10 8 n device bus operation mbm29lv320te/be user bus operations table (byte = = = = v ih ) legend : l = v il , h = v ih , x = v il or v ih , = pulse input. see n dc characteristics for voltage levels. *1: manufacturer and device codes may also be accessed via a command register write sequence. see mbm29lv320te/be command definitions table. *2: see the section on 7. sector group protection in n functional description. *3: we can be v il if oe is v il , oe at v ih initiates the write operations. *4: v cc = 3.3 v 10 % *5: it is also used for the extended sector group protection. *6: conditional exceptions are to be noticed as follows: for mbm29lv320te (sa22, 23) , wp /acc = v ih . for mbm29lv320be (sa0, 1) , wp /acc = v ih . operation ce oe we a 0 a 1 a 6 a 9 dq 15 to dq 0 reset wp / acc auto-select manufacturer code * 1 llhlllv id code h x auto-select device code * 1 llhhllv id code h x extended auto-select device code * 1 l lhhhlv id code h x read * 3 llha 0 a 1 a 6 a 9 d out hx standby h x x x x x x high-z h x output disable l h h x x x x high-z h x write (program/erase) l h l a 0 a 1 a 6 a 9 d in hx enable sector group protection * 2, * 4 lv id lhlv id xhx * 6 verify sector group protection * 2, * 4 llhlhlv id code h x * 6 temporary sector group unprotection * 5 xxxxxxx x v id x * 6 reset (hardware) /standby xxxxxxx high-z l x boot block sector write protection xxxxxxx x x l
mbm29lv320te/be 80/90/10 9 mbm29lv320te/be user bus operations table (byte = = = = v il ) legend : l = v il , h = v ih , x = v il or v ih , = pulse input. see n dc characteristics for voltage levels. *1: manufacturer and device codes may also be accessed via a command register write sequence. see mbm29lv320te/be command definitions table. *2: see the section on 7. sector group protection in n functional description. *3: we can be v il if oe is v il , oe at v ih initiates the write operations. *4: v cc = 3.3 v 10 % *5: it is also used for the extended sector group protection. *6: conditional exceptions are to be noticed as follows: for mbm29lv320te (sa22, 23) , wp /acc = v ih . for mbm29lv320be (sa0, 1) , wp /acc = v ih . operation ce oe we dq 15 /a -1 a 0 a 1 a 6 a 9 dq 7 to dq 0 reset wp / acc auto-select manufacturer code * 1 llh l lllv id code h x auto-select device code * 1 llh l hllv id code h x extended auto-select device code * 1 llh l hhlv id code h x read * 3 llha -1 a 0 a 1 a 6 a 9 d out hx standby h x x x x x x x high-z h x output disable l h h x x x x x high-z h x write (program/erase) l h l a -1 a 0 a 1 a 6 a 9 d in hx enable sector group protection * 2, * 4 lv id llhlv id xhx * 6 verify sector group protection * 2, * 4 llh l lhlv id code h x * 6 temporary sector group unprotection * 5 xxx x xxxx x v id x * 6 reset (hardware) /standby x x x x x x x x high-z l x boot block sector write protection x x x x x x x x x x l
mbm29lv320te/be 80/90/10 10 mbm29lv320te/be command definitions table (continued) command sequence bus write cycles reqd first bus write cycle second bus write cycle third bus write cycle fourth bus read/write cycle fifth bus write cycle sixth bus write cycle addr. data addr. data addr. data addr. data addr. data addr. data read/ reset word 1 xxxh f0h ?????????? byte read/ reset word 3 555h aah 2aah 55h 555h f0h ra rd ???? byte aaah 555h aaah autoselect word 3 555h aah 2aah 55h 555h 90h ?????? byte aaah 555h aaah program word 4 555h aah 2aah 55h 555h a0h pa pd ???? byte aaah 555h aaah chip erase word 6 555h aah 2aah 55h 555h 80h 555h aah 2aah 55h 555h 10h byte aaah 555h aaah aaah 555h aaah sector erase word 6 555h aah 2aah 55h 555h 80h 555h aah 2aah 55h sa 30h byte aaah 555h aaah aaah 555h erase suspend 1 xxxh b0h ?????????? erase resume 1 xxxh 30h ?????????? set to fast mode word 3 555h aah 2aah 55h 555h 20h ?????? byte aaah 555h aaah fast program *1 word 2 xxxh a0h pa pd ???????? byte xxxh reset from fast mode *1 word 2 xxxh 90h xxxh *5 f0h ???????? byte xxxh xxxh extended sector group protection *2 word 4 xxxh 60h spa 60h spa 40h spa sd ???? byte query *3 word 1 55h 98h ?????????? byte aah hi-rom entry word 3 555h aah 2aah 55h 555h 88h ?????? byte aaah 555h aaah hi-rom program *4 word 4 555h aah 2aah 55h 555h a0h (hra) pa pd ???? byte aaah 555h aaah hi-rom exit *4 word 4 555h aah 2aah 55h 555h 90h xxxh 00h ???? byte aaah 555h aaah
mbm29lv320te/be 80/90/10 11 (continued) *1 : this command is valid during fast mode. *2 : this command is valid while reset = v id . *3 : the valid addresses are a 6 to a 0 . *4 : this command is valid during hi-rom mode. *5 : the data "00h" is also acceptable. notes: address bits a 20 to a 11 = x = h or l for all address commands except or program address (pa) and sector address (sa) . bus operations are defined in mbm29lv320te/be user bus operations tables (byte = v ih and byte = v il ) . ra = address of the memory location to be read pa = address of the memory location to be programmed addresses are latched on the falling edge of the write pulse. sa = address of the sector to be erased. the combination of a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , and a 12 will uniquely select any sector. rd = data read from location ra during read operation. pd = data to be programmed at location pa. data is latched on the falling edge of write pulse. spa = sector group address to be protected. set sector group address (sga) and (a 6 , a 1 , a 0 ) = (0, 1, 0) . sd = sector group protection verify data. output 01h at protected sector group addresses and output 00h at unprotected sector group addresses. hra = address of the hi-rom area 29lv320te (top boot type) word mode : 1fffe0h to 1fffffh byte mode : 3fffc0h to 3fffffh 29lv320be (bottom boot type) word mode : 000000h to 000040h byte mode : 000000h to 000080h the system should generate the following address patterns : word mode : 555h or 2aah to addresses a 10 to a 0 byte mode : aaah or 555h to addresses a 10 to a 0 , and a -1 both read/reset commands are functionally equivalent, resetting the device to the read mode. the command combinations not described in mbm29lv320te/be command definition table are illegal.
mbm29lv320te/be 80/90/10 12 mbm29lv320te/be sector group protection verify autoselect codes table *1 : a -1 is for byte mode. *2 : outputs 01h at protected sector group addresses and outputs 00h at unprotected sector group addresses. expanded autoselect code table (b) : byte mode (w) : word mode hz: high-z type a 20 to a 12 a 6 a 1 a 0 a -1 * 1 code (hex) manufactures code sa v il v il v il v il 04h device code mbm29lv320te byte sa v il v il v ih v il f6h word x 22f6h mbm29lv320be byte sa v il v il v ih v il f9h word x 22f9h e xtend device co de mbm29lv320te/be byte sa v il v ih v ih v il 19h word x 0019h sector group protection sector group addresses v il v ih v il v il 01h *2 type code dq 15 dq 14 dq 13 dq 12 dq 11 dq 10 dq 9 dq 8 dq 7 dq 6 dq 5 dq 4 dq 3 dq 2 dq 1 dq 0 manufacturers code 04h a -1 /0 0 0 0 0 0 0000000100 device code mbm29lv 320te (b) f6h a -1 hz hz hz hz hz hz hz 1 1 1 1 0 1 1 0 (w) 22f6h 0001001011110110 mbm29lv 320be (b) f9h a -1 hz hz hz hz hz hz hz 1 1 1 1 1 0 0 1 (w) 22f9h 0001001011111001 extend device code mbm29lv 320te/be (b) 19h a -1 hz hz hz hz hz hz hz 0 0 0 1 1 0 0 1 (w) 0019h 0000000000011001 sector group protec- tion 01h a -1 /0 0 0 0 0 0 0000000001
mbm29lv320te/be 80/90/10 13 n flexible sector-erase architecture sector address table (mbm29lv320te) (continued) sec- tor sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 a 11 sa0 0 0 0 0 0 0 x x x x 64/32 000000h to 00ffffh 000000h to 007fffh sa1 0 0 0 0 0 1 x x x x 64/32 010000h to 01ffffh 008000h to 00ffffh sa2 0 0 0 0 1 0 x x x x 64/32 020000h to 02ffffh 010000h to 017fffh sa3 0 0 0 0 1 1 x x x x 64/32 030000h to 03ffffh 018000h to 01ffffh sa4 0 0 0 1 0 0 x x x x 64/32 040000h to 04ffffh 020000h to 027fffh sa5 0 0 0 1 0 1 x x x x 64/32 050000h to 05ffffh 028000h to 02ffffh sa6 0 0 0 1 1 0 x x x x 64/32 060000h to 06ffffh 030000h to 037fffh sa7 0 0 0 1 1 1 x x x x 64/32 070000h to 07ffffh 038000h to 03ffffh sa8 0 0 1 0 0 0 x x x x 64/32 080000h to 08ffffh 040000h to 047fffh sa9 0 0 1 0 0 1 x x x x 64/32 090000h to 09ffffh 048000h to 04ffffh sa10 0 0 1 0 1 0 x x x x 64/32 0a0000h to 0affffh 050000h to 057fffh sa11 0 0 1 0 1 1 x x x x 64/32 0b0000h to 0bffffh 058000h to 05ffffh sa12 0 0 1 1 0 0 x x x x 64/32 0c0000h to 0cffffh 060000h to 067fffh sa13 0 0 1 1 0 1 x x x x 64/32 0d0000h to 0dffffh 068000h to 06ffffh sa14 0 0 1 1 1 0 x x x x 64/32 0e0000h to 0effffh 070000h to 077fffh sa15 0 0 1 1 1 1 x x x x 64/32 0f0000h to 0fffffh 078000h to 07ffffh sa16 0 1 0 0 0 0 x x x x 64/32 100000h to 10ffffh 080000h to 087fffh sa17 0 1 0 0 0 1 x x x x 64/32 110000h to 11ffffh 088000h to 08ffffh sa18 0 1 0 0 1 0 x x x x 64/32 120000h to 12ffffh 090000h to 097fffh sa19 0 1 0 0 1 1 x x x x 64/32 130000h to 13ffffh 098000h to 09ffffh sa20 0 1 0 1 0 0 x x x x 64/32 140000h to 14ffffh 0a0000h to 0a7fffh sa21 0 1 0 1 0 1 x x x x 64/32 150000h to 15ffffh 0a8000h to 0affffh sa22 0 1 0 1 1 0 x x x x 64/32 160000h to 16ffffh 0b0000h to 0b7fffh sa23 0 1 0 1 1 1 x x x x 64/32 170000h to 17ffffh 0b8000h to 0bffffh sa24 0 1 1 0 0 0 x x x x 64/32 180000h to 18ffffh 0c0000h to 0c7fffh sa25 0 1 1 0 0 1 x x x x 64/32 190000h to 19ffffh 0c8000h to 0cffffh sa26 0 1 1 0 1 0 x x x x 64/32 1a0000h to 1affffh 0d0000h to 0d7fffh sa27 0 1 1 0 1 1 x x x x 64/32 1b0000h to 1bffffh 0d8000h to 0dffffh sa28 0 1 1 1 0 0 x x x x 64/32 1c0000h to 1cffffh 0e0000h to 0e7fffh sa29 0 1 1 1 0 1 x x x x 64/32 1d0000h to 1dffffh 0e8000h to 0effffh sa30 0 1 1 1 1 0 x x x x 64/32 1e0000h to 1effffh 0f0000h to 0f7fffh sa31 0 1 1 1 1 1 x x x x 64/32 1f0000h to 1fffffh 0f8000h to 0fffffh
mbm29lv320te/be 80/90/10 14 (continued) sec- tor sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 a 11 sa32 1 0 0 0 0 0 x x x x 64/32 200000h to 20ffffh 100000h to 107fffh sa33 1 0 0 0 0 1 x x x x 64/32 210000h to 21ffffh 108000h to 10ffffh sa34 1 0 0 0 1 0 x x x x 64/32 220000h to 22ffffh 110000h to 117fffh sa35 1 0 0 0 1 1 x x x x 64/32 230000h to 23ffffh 118000h to 11ffffh sa36 1 0 0 1 0 0 x x x x 64/32 240000h to 24ffffh 120000h to 127fffh sa37 1 0 0 1 0 1 x x x x 64/32 250000h to 25ffffh 128000h to 12ffffh sa38 1 0 0 1 1 0 x x x x 64/32 260000h to 26ffffh 130000h to 137fffh sa39 1 0 0 1 1 1 x x x x 64/32 270000h to 27ffffh 138000h to 13ffffh sa40 1 0 1 0 0 0 x x x x 64/32 280000h to 28ffffh 140000h to 147fffh sa41 1 0 1 0 0 1 x x x x 64/32 290000h to 29ffffh 148000h to 14ffffh sa42 1 0 1 0 1 0 x x x x 64/32 2a0000h to 2affffh 150000h to 157fffh sa43 1 0 1 0 1 1 x x x x 64/32 2b0000h to 2bffffh 158000h to 15ffffh sa44 1 0 1 1 0 0 x x x x 64/32 2c0000h to 2cffffh 160000h to 167fffh sa45 1 0 1 1 0 1 x x x x 64/32 2d0000h to 2dffffh 168000h to 16ffffh sa46 1 0 1 1 1 0 x x x x 64/32 2e0000h to 2effffh 170000h to 177fffh sa47 1 0 1 1 1 1 x x x x 64/32 2f0000h to 2fffffh 178000h to 17ffffh sa48 1 1 0 0 0 0 x x x x 64/32 300000h to 30ffffh 180000h to 187fffh sa49 1 1 0 0 0 1 x x x x 64/32 310000h to 31ffffh 188000h to 18ffffh sa50 1 1 0 0 1 0 x x x x 64/32 320000h to 32ffffh 190000h to 197fffh sa51 1 1 0 0 1 1 x x x x 64/32 330000h to 33ffffh 198000h to 19ffffh sa52 1 1 0 1 0 0 x x x x 64/32 340000h to 34ffffh 1a0000h to 1a7fffh sa53 1 1 0 1 0 1 x x x x 64/32 350000h to 35ffffh 1a8000h to 1affffh sa54 1 1 0 1 1 0 x x x x 64/32 360000h to 36ffffh 1b0000h to 1b7fffh sa55 1 1 0 1 1 1 x x x x 64/32 370000h to 37ffffh 1b8000h to 1bffffh sa56 1 1 1 0 0 0 x x x x 64/32 380000h to 38ffffh 1c0000h to 1c7fffh sa57 1 1 1 0 0 1 x x x x 64/32 390000h to 39ffffh 1c8000h to 1cffffh sa58 1 1 1 0 1 0 x x x x 64/32 3a0000h to 3affffh 1d0000h to 1d7fffh sa59 1 1 1 0 1 1 x x x x 64/32 3b0000h to 3bffffh 1d8000h to 1dffffh sa60 1 1 1 1 0 0 x x x x 64/32 3c0000h to 3cffffh 1e0000h to 1e7fffh sa61 1 1 1 1 0 1 x x x x 64/32 3d0000h to 3dffffh 1e8000h to 1effffh sa62 1 1 1 1 1 0 x x x x 64/32 3e0000h to 3effffh 1f0000h to 1f7fffh sa63 1 1 1 1 1 1 0 0 0 x 8/4 3f0000h to 3f1fffh 1f8000h to 1f8fffh sa64 1 1 1 1 1 1 0 0 1 x 8/4 3f2000h to 3f3fffh 1f9000h to 1f9fffh
mbm29lv320te/be 80/90/10 15 (continued) note : the address range is a 20 : a -1 if in byte mode (byte = v il ) . the address range is a 20 : a 0 if in word mode (byte = v ih ) . sec- tor sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 a 11 sa65 1 1 1 1 1 1 0 1 0 x 8/4 3f4000h to 3f5fffh 1fa000h to 1fafffh sa66 1 1 1 1 1 1 0 1 1 x 8/4 3f6000h to 3f7fffh 1fb000h to 1fbfffh sa67 1 1 1 1 1 1 1 0 0 x 8/4 3f8000h to 3f9fffh 1fc000h to 1fcfffh sa68 1 1 1 1 1 1 1 0 1 x 8/4 3fa000h to 3fbfffh 1fd000h to 1fdfffh sa69 1 1 1 1 1 1 1 1 0 x 8/4 3fc000h to 3fdfffh 1fe000h to 1fefffh sa70 1 1 1 1 1 1 1 1 1 x 8/4 3fe000h to 3fffffh 1ff000h to 1fffffh
mbm29lv320te/be 80/90/10 16 sector address table (mbm29lv320be) (continued) sec- tor sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 a 11 sa70 1 1 1 1 1 1 x x x x 64/32 3f0000h to 3fffffh 1f8000h to 1fffffh sa69 1 1 1 1 1 0 x x x x 64/32 3e0000h to 3effffh 1f0000h to 1f7fffh sa68 1 1 1 1 0 1 x x x x 64/32 3d0000h to 3dffffh 1e8000h to 1effffh sa67 1 1 1 1 0 0 x x x x 64/32 3c0000h to 3cffffh 1e0000h to 1e7fffh sa66 1 1 1 0 1 1 x x x x 64/32 3b0000h to 3bffffh 1d8000h to 1dffffh sa65 1 1 1 0 1 0 x x x x 64/32 3a0000h to 3affffh 1d0000h to 1d7fffh sa64 1 1 1 0 0 1 x x x x 64/32 390000h to 39ffffh 1c8000h to 1cffffh sa63 1 1 1 0 0 0 x x x x 64/32 380000h to 38ffffh 1c0000h to 1c7fffh sa62 1 1 0 1 1 1 x x x x 64/32 370000h to 37ffffh 1b8000h to 1bffffh sa61 1 1 0 1 1 0 x x x x 64/32 360000h to 36ffffh 1b0000h to 1b7fffh sa60 1 1 0 1 0 1 x x x x 64/32 350000h to 35ffffh 1a8000h to 1affffh sa59 1 1 0 1 0 0 x x x x 64/32 340000h to 34ffffh 1a0000h to 1a7fffh sa58 1 1 0 0 1 1 x x x x 64/32 330000h to 33ffffh 198000h to 19ffffh sa57 1 1 0 0 1 0 x x x x 64/32 320000h to 32ffffh 190000h to 197fffh sa56 1 1 0 0 0 1 x x x x 64/32 310000h to 31ffffh 188000h to 18ffffh sa55 1 1 0 0 0 0 x x x x 64/32 300000h to 30ffffh 180000h to 187fffh sa54 1 0 1 1 1 1 x x x x 64/32 2f0000h to 2fffffh 178000h to 17ffffh sa53 1 0 1 1 1 0 x x x x 64/32 2e0000h to 2effffh 170000h to 177fffh sa52 1 0 1 1 0 1 x x x x 64/32 2d0000h to 2dffffh 168000h to 16ffffh sa51 1 0 1 1 0 0 x x x x 64/32 2c0000h to 2cffffh 160000h to 167fffh sa50 1 0 1 0 1 1 x x x x 64/32 2b0000h to 2bffffh 158000h to 15ffffh sa49 1 0 1 0 1 0 x x x x 64/32 2a0000h to 2affffh 150000h to 157fffh sa48 1 0 1 0 0 1 x x x x 64/32 290000h to 29ffffh 148000h to 14ffffh sa47 1 0 1 0 0 0 x x x x 64/32 280000h to 28ffffh 140000h to 147fffh sa46 1 0 0 1 1 1 x x x x 64/32 270000h to 27ffffh 138000h to 13ffffh sa45 1 0 0 1 1 0 x x x x 64/32 260000h to 26ffffh 130000h to 137fffh sa44 1 0 0 1 0 1 x x x x 64/32 250000h to 25ffffh 128000h to 12ffffh sa43 1 0 0 1 0 0 x x x x 64/32 240000h to 24ffffh 120000h to 127fffh sa42 1 0 0 0 1 1 x x x x 64/32 230000h to 23ffffh 118000h to 11ffffh sa41 1 0 0 0 1 0 x x x x 64/32 220000h to 22ffffh 110000h to 117fffh sa40 1 0 0 0 0 1 x x x x 64/32 210000h to 21ffffh 108000h to 10ffffh sa39 1 0 0 0 0 0 x x x x 64/32 200000h to 20ffffh 100000h to 107fffh sa38 0 1 1 1 1 1 x x x x 64/32 1f0000h to 1fffffh 0f8000h to 0fffffh
mbm29lv320te/be 80/90/10 17 (continued) sec- tor sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 a 11 sa37 0 1 1 1 1 0 x x x x 64/32 1e0000h to 1effffh 0f0000h to 0f7fffh sa36 0 1 1 1 0 1 x x x x 64/32 1d0000h to 1dffffh 0e8000h to 0effffh sa35 0 1 1 1 0 0 x x x x 64/32 1c0000h to 1cffffh 0e0000h to 0e7fffh sa34 0 1 1 0 1 1 x x x x 64/32 1b0000h to 1bffffh 0d8000h to 0dffffh sa33 0 1 1 0 1 0 x x x x 64/32 1a0000h to 1affffh 0d0000h to 0d7fffh sa32 0 1 1 0 0 1 x x x x 64/32 190000h to 19ffffh 0c8000h to 0cffffh sa31 0 1 1 0 0 0 x x x x 64/32 180000h to 18ffffh 0c0000h to 0c7fffh sa30 0 1 0 1 1 1 x x x x 64/32 170000h to 17ffffh 0b8000h to 0bffffh sa29 0 1 0 1 1 0 x x x x 64/32 160000h to 16ffffh 0b0000h to 0b7fffh sa28 0 1 0 1 0 1 x x x x 64/32 150000h to 15ffffh 0a8000h to 0affffh sa27 0 1 0 1 0 0 x x x x 64/32 140000h to 14ffffh 0a0000h to 0a7fffh sa26 0 1 0 0 1 1 x x x x 64/32 130000h to 13ffffh 098000h to 09ffffh sa25 0 1 0 0 1 0 x x x x 64/32 120000h to 12ffffh 090000h to 097fffh sa24 0 1 0 0 0 1 x x x x 64/32 110000h to 11ffffh 088000h to 08ffffh sa23 0 1 0 0 0 0 x x x x 64/32 100000h to 10ffffh 080000h to 087fffh sa22 0 0 1 1 1 1 x x x x 64/32 0f0000h to 0fffffh 078000h to 07ffffh sa21 0 0 1 1 1 0 x x x x 64/32 0e0000h to 0effffh 070000h to 077fffh sa20 0 0 1 1 0 1 x x x x 64/32 0d0000h to 0dffffh 068000h to 06ffffh sa19 0 0 1 1 0 0 x x x x 64/32 0c0000h to 0cffffh 060000h to 067fffh sa18 0 0 1 0 1 1 x x x x 64/32 0b0000h to 0bffffh 058000h to 05ffffh sa17 0 0 1 0 1 0 x x x x 64/32 0a0000h to 0affffh 050000h to 057fffh sa16 0 0 1 0 0 1 x x x x 64/32 090000h to 09ffffh 048000h to 04ffffh sa15 0 0 1 0 0 0 x x x x 64/32 080000h to 08ffffh 040000h to 047fffh sa14 0 0 0 1 1 1 x x x x 64/32 070000h to 07ffffh 038000h to 03ffffh sa13 0 0 0 1 1 0 x x x x 64/32 060000h to 06ffffh 030000h to 037fffh sa12 0 0 0 1 0 1 x x x x 64/32 050000h to 05ffffh 028000h to 02ffffh sa11 0 0 0 1 0 0 x x x x 64/32 040000h to 04ffffh 020000h to 027fffh sa10 0 0 0 0 1 1 x x x x 64/32 030000h to 03ffffh 018000h to 01ffffh sa9 0 0 0 0 1 0 x x x x 64/32 020000h to 02ffffh 010000h to 017fffh sa8 0 0 0 0 0 1 x x x x 64/32 010000h to 01ffffh 008000h to 00ffffh sa7 0 0 0 0 0 0 1 1 1 x 8/4 00e000h to 00ffffh 007000h to 007fffh sa6 0 0 0 0 0 0 1 1 0 x 8/4 00c000h to 00dfffh 006000h to 006fffh sa5 0 0 0 0 0 0 1 0 1 x 8/4 00a000h to 00bfffh 005000h to 005fffh
mbm29lv320te/be 80/90/10 18 (continued) note : the address range is a 20 : a -1 if in byte mode (byte = v il ) . the address range is a 20 : a 0 if in word mode (byte = v ih ) . sec- tor sector address sector size (kbytes/ kwords) ( 8) address range ( 16) address range a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 a 11 sa4 0 0 0 0 0 0 1 0 0 x 8/4 008000h to 009fffh 004000h to 004fffh sa3 0 0 0 0 0 0 0 1 1 x 8/4 006000h to 007fffh 003000h to 003fffh sa2 0 0 0 0 0 0 0 1 0 x 8/4 004000h to 005fffh 002000h to 002fffh sa1 0 0 0 0 0 0 0 0 1 x 8/4 002000h to 003fffh 001000h to 001fffh sa0 0 0 0 0 0 0 0 0 0 x 8/4 000000h to 001fffh 000000h to 000fffh
mbm29lv320te/be 80/90/10 19 sector group address table (mbm29lv320te) (top boot block) sector group a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 sectors sga0 0 0 0 0xxxxx sa0 to sa3 sga1 0 0 0 1xxxxx sa4 to sa7 sga2 0 0 1 0xxxxxsa8 to sa11 sga3 0 0 1 1xxxxxsa12 to sa15 sga4 0 1 0 0xxxxxsa16 to sa19 sga5 0 1 0 1xxxxxsa20 to sa23 sga6 0 1 1 0xxxxxsa24 to sa27 sga7 0 1 1 1xxxxxsa28 to sa31 sga8 1 0 0 0xxxxxsa32 to sa35 sga9 1 0 0 1xxxxxsa36 to sa39 sga10 1 0 1 0xxxxxsa40 to sa43 sga11 1 0 1 1xxxxxsa44 to sa47 sga12 1 1 0 0xxxxxsa48 to sa51 sga13 1 1 0 1xxxxxsa52 to sa55 sga14 1 1 1 0xxxxxsa56 to sa59 sga15 1 1 1 1 00 x x x sa60 to sa62 01 10 sga16 111111000 sa63 sga17 111111001 sa64 sga18 111111010 sa65 sga19 111111011 sa66 sga20 111111100 sa67 sga21 111111101 sa68 sga22 111111110 sa69 sga23 111111111 sa70
mbm29lv320te/be 80/90/10 20 sector group address table (mbm29lv320be) (bottom boot block) sector group a 20 a 19 a 18 a 17 a 16 a 15 a 14 a 13 a 12 sectors sga0 000000000 sa0 sga1 000000001 sa1 sga2 000000010 sa2 sga3 000000011 sa3 sga4 000000100 sa4 sga5 000000101 sa5 sga6 000000110 sa6 sga7 000000111 sa7 sga8 0000 01 x x x sa8 to sa10 10 11 sga9 0 0 0 1xxxxxsa11 to sa14 sga10 0 0 1 0xxxxxsa15 to sa18 sga11 0 0 1 1xxxxxsa19 to sa22 sga12 0 1 0 0xxxxxsa23 to sa26 sga13 0 1 0 1xxxxxsa27 to sa30 sga14 0 1 1 0xxxxxsa31 to sa34 sga15 0 1 1 1xxxxxsa35 to sa38 sga16 1 0 0 0xxxxxsa39 to sa42 sga17 1 0 0 1xxxxxsa43 to sa46 sga18 1 0 1 0xxxxxsa47 to sa50 sga19 1 0 1 1xxxxxsa51 to sa54 sga20 1 1 0 0xxxxxsa55 to sa58 sga21 1 1 0 1xxxxxsa59 to sa62 sga22 1 1 1 0xxxxxsa63 to sa66 sga23 1 1 1 1xxxxxsa67 to sa70
mbm29lv320te/be 80/90/10 21 common flash memory interface code table (continued) description a 6 to a 0 dq 15 to dq 0 query-unique ascii string qry 10h 11h 12h 0051h 0052h 0059h primary oem command set 02h : amd/fj standard type 13h 14h 0002h 0000h address for primary extended table 15h 16h 0040h 0000h alternate oem command set (00h = not applicable) 17h 18h 0000h 0000h address for alternate oem extended table 19h 1ah 0000h 0000h v cc min (write/erase) dq 7 to dq 4 : 1 v/bit, dq 3 to dq 0 : 100 mv/bit 1bh 0027h v cc max (write/erase) dq 7 to dq 4 : 1 v/bit, dq 3 to dq 0 : 100 mv/bit 1ch 0036h v pp min voltage 1dh 0000h v pp max voltage 1eh 0000h typical timeout per single byte/word write 2 n m s 1fh 0004h typical timeout for min size buffer write 2 n m s 20h 0000h typical timeout per individual block erase 2 n ms 21h 000ah typical timeout for full chip erase 2 n ms 22h 0000h max timeout for byte/word write 2 n times typical 23h 0005h max timeout for buffer write 2 n times typical 24h 0000h max timeout per individual block erase 2 n times typical 25h 0004h max timeout for full chip erase 2 n times typical 26h 0000h device size = 2 n byte 27h 0016h flash device interface description 28h 29h 0002h 0000h max number of byte in multi-byte write = 2 n 2ah 2bh 0000h 0000h number of erase block regions within device 2ch 0002h erase block region 1 information 2dh 2eh 2fh 30h 0007h 0000h 0020h 0000h erase block region 2 information 31h 32h 33h 34h 003eh 0000h 0000h 0001h
mbm29lv320te/be 80/90/10 22 (continued) description a 6 to a 0 dq 15 to dq 0 query-unique ascii string pri 40h 41h 42h 0050h 0052h 0049h major version number, ascii 43h 0031h minor version number, ascii 44h 0031h address sensitive unlock 00h = required 01h = not required 45h 0000h erase suspend 00h = not supported 01h = to r e a d o n l y 02h = to r e a d & w r i t e 46h 0002h sector group protection 00h = not supported x = number of sectors in per group 47h 0004h sector group temporary unprotection 00h = not supported 01h = supported 48h 0001h sector group protection algorithm 49h 0004h number of sector for bank 2 00h = not supported 4ah 0000h burst mode type 00h = not supported 4bh 0000h page mode type 00h = not supported 4ch 0000h v acc (acceleration) supply minimum 00h = not supported, dq 7 to dq 4 : 1 v/bit, dq 3 to dq 0 : 100 mv/bit 4dh 00b5h v acc (acceleration) supply maximum 00h = not supported, dq 7 to dq 4 : 1 v/bit, dq 3 to dq 0 : 100 mv/bit 4eh 00c5h boot type 02h = mbm29lv320be 03h = mbm29lv320te 4fh 00xxh
mbm29lv320te/be 80/90/10 23 n functional description 1. read mode the device has two control functions which must be satisfied in order to obtain data at the outputs. ce is the power control and should be used for a device selection. oe is the output control and should be used to gate data to the output pins if a device is selected. address access time (t acc ) is equal to delay from stable addresses to valid output data. the chip enable access time (t ce ) is the delay from stable addresses and stable ce to valid data at the output pins. the output enable access time is the delay from the falling edge of oe to valid data at the output pins. (assuming the addresses have been stable for at least t acc -t oe time.) when reading out data without changing addresses after power-up, it is necessary to input hardware reset or to change ce pin from h or l. 2. standby mode there are two ways to implement the standby mode on the device, one using both the ce and reset pins; the other via the reset pin only. when using both pins, a cmos standby mode is achieved with ce and reset inputs both held at v cc 0.3 v. under this condition the current consumed is less than 5 m a max during embedded algorithm operation, v cc active current (i cc2 ) is required even ce = h. the device can be read with standard access time (t ce ) from either of these standby modes. when using the reset pin only, a cmos standby mode is achieved with reset input held at v ss 0.3 v (ce = h or l) . under this condition the current consumed is less than 5 m a max once the reset pin is taken high, the device requires t rh as wake up time for outputs to be valid for read access. in the standby mode the outputs are in the high impedance state, independently of the oe input. 3. automatic sleep mode there is a function called automatic sleep mode to restrain power consumption during read-out of the device data. this mode can be useful in the application such as a handy terminal which requires low power consumption. to activate this mode, the device automatically switches themselves to low power mode when the device ad- dresses remain stable during access time of 150 ns. it is not necessary to control ce , we , and oe on the mode. under the mode, the current consumed is typically 1 m a (cmos level) . during simultaneous operation, v cc active current (i cc2 ) is required. since the data are latched during this mode, the data are read-out continuously. if the addresses are changed, the mode is canceled automatically, and the device read the data for changed addresses. 4. output disable with the oe input at a logic high level (v ih ) , output from the device is disabled. this will cause the output pins to be in a high impedance state. 5. autoselect the autoselect mode allows the reading out of a binary code from the device and will identify its manufacturer and type. this mode is intended for use by programming equipment for the purpose of automatically matching the device to be programmed with its corresponding programming algorithm. this mode is functional over the entire temperature range of the device. to activate this mode, the programming equipment must force v id (11.5 v to 12.5 v) on address pin a 9 . two identifier bytes may then be sequenced from the device outputs by toggling address a 0 from v il to v ih . all addresses are dont cares except a 6 , a 1 , and a 0 (a -1 ) . (see mbm29lv320te/be user bus operations tables (byte = v ih and byte = v il ) in n device bus operations.) the manufacturer and device codes may also be read via the command register, for instances when the device is erased or programmed in a system without access to high voltage on the a 9 pin. the command sequence is illustrated in mbm29lv320te/be command definitions table ( n device bus operations) (see 2. autoselect command in n comand difinitions) .
mbm29lv320te/be 80/90/10 24 word 0 (a 0 = v il ) represents the manufacturers code (fujitsu = 04h) and word 1 (a 0 = v ih ) represents the device identifier code. word 3 (a 1 = a 0 = v ih ) represents the extended device code. these three bytes/words are given in mbm29lv320te/be sector group protection verify autoselect codes tableand expanded autoselect code ta b l e ( n device bus operations) . in order to read the proper device codes when executing the autoselect, a 1 must be v il . (see mbm29lv320te/be sector group protection verify autoselect codes table and ex- panded autoselect code table in n device bus operations.) 6. write the device erasure and programming are accomplished via the command register. the contents of the register serve as inputs to the internal state machine. the state machine outputs dictate the function of the device. the command register itself does not occupy any addressable memory location. the register is a latch used to store the commands, along with the address and data information needed to execute the command. the com- mand register is written by bringing we to v il , while ce is at v il and oe is at v ih . addresses are latched on the falling edge of we or ce , whichever happens later; while data is latched on the rising edge of we or ce , whichever happens first. standard microprocessor write timings are used. see read only operation characteristics in n ac characteristics for specific timing parameters. 7. sector group protection the device features hardware sector group protection. this feature will disable both program and erase opera- tions in any combination of twenty five sector groups of memory. (see sector group address tables (mbm29lv320te/be) in n flexible sector-erase architecture). the sector group protection feature is enabled using programming equipment at the users site. the device is shipped with all sector groups unpro- tected. to activate this mode, the programming equipment must force v id on address pin a 9 and control pin oe , (suggest v id = 11.5 v) , ce = v il and a 6 = a 0 = v il , a 1 = v ih . the sector group addresses (a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , and a 12 ) should be set to the sector to be protected. sector address tables (mbm29lv320te/be) in n flexible sector-erase architecture define the sector address for each of the seventy one (71) individual sectors, and sector group address tables (mbm29lv320te/be) in n flexible sector-erase architecture define the sector group address for each of the twenty five (25) individual group sectors. programming of the protection circuitry begins on the falling edge of the we pulse and is terminated with the rising edge of the same. sector group addresses must be held constant during the we pulse. see 14. sector group protection timing diagram in n timing diagram and 5. sector group protection algorithm in n flow chart for sector group protection waveforms and algorithm. to verify programming of the protection circuitry, the programming equipment must force v id on address pin a 9 with ce and oe at v il and we at v ih . scanning the sector group addresses (a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , and a 12 ) while (a 6 , a 1 , a 0 ) = (0, 1, 0) will produce a logical 1 code at device output dq 0 for a protected sector. otherwise the device will produce 0 for unprotected sector. in this mode, the lower order addresses, except for a 0 , a 1 , and a 6 are dont cares. address locations with a 1 = v il are reserved for autoselect manufacturer and device codes. a -1 requires to apply to v il on byte mode. it is also possible to determine if a sector group is protected in the system by writing an autoselect command. performing a read operation at the address location xx02h, where the higher order addresses (a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , and a 12 ) are the desired sector group address will produce a logical 1 at dq 0 for a protected sector group. see mbm29lv320te/be sector group protection verify autoselect codes table and expanded autoselect code table in n device bus operations for autoselect codes. 8. temporary sector group unprotection this feature allows temporary unprotection of previously protected sector groups of the device in order to change data. the sector group unprotection mode is activated by setting the reset pin to high voltage (v id ) . during this mode, formerly protected sector groups can be programmed or erased by selecting the sector group ad- dresses. once the v id is taken away from the reset pin, all the previously protected sector groups will be protected again. see 15. temporary sector group unprotection timing diagram in n timing diagram and 6. temporary sector group unprotection algorithm in n flow chart.
mbm29lv320te/be 80/90/10 25 9. extended sector group protection in addition to normal sector group protection, the device has extended sector group protection as extended function. this function enables to protect sector group by forcing v id on reset pin and write a command sequence. unlike conventional procedure, it is not necessary to force v id and control timing for control pins. the only reset pin requires v id for sector group protection in this mode. the extended sector group protection requires v id on reset pin. with this condition, the operation is initiated by writing the set-up command (60h) into the command register. then, the sector group addresses pins (a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 and a 12 ) and (a 6 , a 1 , a 0 ) = (0, 1, 0) should be set to the sector group to be protected (recommend to set v il for the other addresses pins) , and write extended sector group protection command (60h) . a sector group is typically protected in 250 m s. to verify programming of the protection circuitry, the sector group addresses pins (a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 and a 12 ) and (a 6 , a 1 , a 0 ) = (0, 1, 0) should be set and write a command (40h) . following the command write, a logical 1 at device output dq 0 will produce for protected sector in the read operation. if the output is logical 0, please repeat to write extended sector group protection command (60h) again. to terminate the operation, it is necessary to set reset pin to v ih . (see 16. extended sector group protection timing diagram in n timing diagram and 7. extended sector group protection algorithm in n flow chart.) 10. reset hardware reset the device may be reset by driving the reset pin to v il . the reset pin has a pulse requirement and has to be kept low (v il ) for at least t rp in order to properly reset the internal state machine. any operation in the process of being executed will be terminated and the internal state machine will be reset to the read mode t ready after the reset pin is driven low. furthermore, once the reset pin goes high, the device requires an additional t rh before it will allow read access. when the reset pin is low, the device will be in the standby mode for the duration of the pulse and all the data output pins will be tri-stated. if a hardware reset occurs during a program or erase operation, the data at that particular location will be corrupted. please note that the ry/by output signal should be ignored during the reset pulse. see 10. reset , ry/by timing diagram in n timing diagram for the timing diagram. see 8. temporary sector group unprotection for additional functionality. 11. boot block sector protection the write protection function provides a hardware method of protecting certain boot sectors without using v id . this function is one of two provided by the wp /acc pin. if the system asserts v il on the wp /acc pin, the device disables program and erase functions in the two outermost 8 k byte boot sectors independently of whether those sectors are protected or unprotected using the method described in sector protection/unprotection. the two outermost 8 k byte boot sectors are the two sectors containing the lowest addresses in a bottom-boot-configured device, or the two sectors containing the highest addresses in a top-boot-congfigured device. (mbm29lv320te : sa69 and sa70, mbm29lv320be : sa0 and sa1) if the system asserts v ih on the wp /acc pin, the device reverts to whether the two outermost 8 k byte boot sectors were last set to be protected or unprotected. that is, sector protection or unprotection for these two sectors depends on whether they were last protected or unprotected using the method described in sector protection/unprotection. 12. accelerated program operation the device offers accelerated program operation which enables the programming in high speed. if the system asserts v acc to the wp /acc pin, the device automatically enters the acceleration mode and the time required for program operation will reduce to about 60 % . this function is primarily intended to allow high speed program, so caution is needed as the sector group will temporarily be unprotected. the system would use a fast program command sequence when programming during acceleration mode. set command to fast mode and reset command from fast mode are not necessary. when the device enters the acceleration mode, the device automatically set to fast mode. therefore, the pressent sequence could be used for programming and detection of completion during acceleration mode. removing v acc from the wp /acc pin returns the device to normal operation. do not remove v acc from wp / acc pin while programming. see 17. accelerated program timing diagram in n timing diagram.
mbm29lv320te/be 80/90/10 26 n command definitions the device operations are selected by writing specific address and data sequences into the command register. writing incorrect address and data values or writing them in the improper sequence will reset the device to the read mode. mbm29lv320te/be command definitions table in n device bus operations defines the valid register command sequences. note that the erase suspend (b0h) and erase resume (30h) commands are valid only while the sector erase operation is in progress. moreover both read/reset commands are functionally equivalent, resetting the device to the read mode. please note that commands are always written at dq 7 to dq 0 and dq 15 to dq 8 bits are ignored. 1. read/reset command in order to return from autoselect mode or exceeded timing limits (dq 5 = 1) to read/reset mode, the read/ reset operation is initiated by writing the read/reset command sequence into the command register. micro- processor read cycles retrieve array data from the memory. the device remain enabled for reads until the command register contents are altered. the device will automatically power-up in the read/reset state. in this case, a command sequence is not required to read data. standard microprocessor read cycles will retrieve array data. this default value ensures that no spurious alteration of the memory content occurs during the power transition. see n ac characteristics for the specific timing parameters. 2. autoselect command flash memories are intended for use in applications where the local cpu alters memory contents. as such, manufacture and device codes must be accessible while the device resides in the target system. prom pro- grammers typically access the signature codes by raising a 9 to a high voltage. however, multiplexing high voltage onto the address lines is not generally desired system design practice. the device contains an autoselect command operation to supplement traditional prom programming method- ology. the operation is initiated by writing the autoselect command sequence into the command register. following the command write, a read cycle from address (xx) 00h retrieves the manufacture code of 04h. a read cycle from address (xx) 01h for 16 ( (xx) 02h for 8) returns the device code. a read cycle from address (xx) 03h for 16 ( (xx) 06h for 8) returns the extended device code. (see mbm29lv320te/be sector group protection verify autoselect codes table and expanded autoselect code table in n device bus opera- tions.) the sector state (protection or unprotection) will be informed by address (xx) 02h for 16 ( (xx) 04h for 8) . scanning the sector group addresses (a 20 , a 19 , a 18 , a 17 , a 16 , a 15 , a 14 , a 13 , and a 12 ) while (a 6 , a 1 , a 0 ) = (0, 1, 0) will produce a logical 1 at device output dq 0 for a protected sector group. the programming verification should be performed by verify sector group protection on the protected sector. (see mbm29lv320te/be user bus operations tables (byte = v ih and byte = v il ) in n device bus operations.) to terminate the operation, it is necessary to write the read/reset command sequence into the register. to execute the autoselect command during the operation, writing read/reset command sequence must precede the autoselect command. 3. byte/word programming the device is programmed on a byte-by-byte (or word-by-word) basis. programming is a four bus cycle operation. there are two unlock write cycles. these are followed by the program set-up command and data write cycles. addresses are latched on the falling edge of ce or we , whichever happens later and the data is latched on the rising edge of ce or we , whichever happens first. the rising edge of ce or we (whichever happens first) begins programming. upon executing the embedded program algorithm command sequence, the system is not required to provide further controls or timings. the device will automatically provide adequate internally generated pro- gram pulses and verify the programmed cell margin. the system can determine the status of the program operation by using dq 7 (data polling) , dq 6 (toggle bit) , or ry/by . the data polling and toggle bit must be performed at the memory location which is being programmed.
mbm29lv320te/be 80/90/10 27 the automatic programming operation is completed when the data on dq 7 is equivalent to data written to this bit at which time the device return to the read mode and addresses are no longer latched. (see hardware sequence flags table.) therefore, the device requires that a valid address to the device be supplied by the system at this particular instance of time. hence, data polling must be performed at the memory location which is being programmed. any commands written to the chip during this period will be ignored. if hardware reset occurs during the pro- gramming operation, it is impossible to guarantee the data are being written. programming is allowed in any sequence and across sector boundaries. beware that a data 0 cannot be programmed back to a 1. attempting to do so may either hang up the device or result in an apparent success according to the data polling algorithm but a read from read/reset mode will show that the data is still 0. only erase operations can convert 0s to 1s. 1. embedded program tm algorithm in n flow chart illustrates the embedded program tm algorithm using typical command strings and bus operations. 4. chip erase chip erase is a six bus cycle operation. there are two unlock write cycles. these are followed by writing the set-up command. two more unlock write cycles are then followed by the chip erase command. chip erase does not require the user to program the device prior to erase. upon executing the embedded erase algorithm command sequence the device will automatically program and verify the entire memory for an all zero data pattern prior to electrical erase (preprogram function) . the system is not required to provide any controls or timings during these operations. the system can determine the status of the erase operation by using dq 7 (data polling) , dq 6 (toggle bit) , or ry/by . the chip erase begins on the rising edge of the last ce or we , whichever happens first in the command sequence and terminates when the data on dq 7 is 1 (see 12. write operation status.) at which time the device returns to read the mode. chip erase time; sector erase time all sectors + chip program time (preprogramming) 2. embedded erase tm algorithm in n flow chart illustrates the embedded erase tm algorithm using typical command strings and bus operations. 5. sector erase sector erase is a six bus cycle operation. there are two unlock write cycles. these are followed by writing the set-up command. two more unlock write cycles are then followed by the sector erase command. the sector address (any address location within the desired sector) is latched on the falling edge of ce or we whichever happens later, while the command (data = 30h) is latched on the rising edge of ce or we which happens first. after time-out of t tow from the rising edge of the last sector erase command, the sector erase operation will begin. multiple sectors may be erased concurrently by writing the six bus cycle operations on mbm29lv320te/be command definitions table in n device bus operations. this sequence is followed with writes of the sector erase command to addresses in other sectors desired to be concurrently erased. the time between writes must be less than t tow otherwise that command will not be accepted and erasure will not start. it is recommended that processor interrupts be disabled during this time to guarantee this condition. the interrupts can be re-enabled after the last sector erase command is written. a time-out of t tow from the rising edge of last ce or we whichever happens first will initiate the execution of the sector erase command(s). if another falling edge of ce or we , whichever happens first occurs within the t tow time-out window the timer is reset. (monitor dq 3 to determine if the sector erase timer window is still open, see 16. dq 3 , sector erase timer.) any command other than sector erase or erase suspend during this time-out period will reset the device to the read mode, ignoring the previous command string. resetting the device once execution has begun will corrupt the data in the sector. in that case, restart the erase on those sectors and allow them to complete. (see 12. write operation status for sector erase timer operation.) loading the sector erase buffer may be done in any sequence and with any number of sectors (0 to 70) . sector erase does not require the user to program the device prior to erase. the device automatically program all memory locations in the sector (s) to be erased prior to electrical erase (preprogram function) . when erasing
mbm29lv320te/be 80/90/10 28 a sector or sectors the remaining unselected sectors are not affected. the system is not required to provide any controls or timings during these operations. the system can determine the status of the erase operation by using dq 7 (data polling) , dq 6 (toggle bit) , or ry/by . the sector erase begins after the t tow time out from the rising edge of ce or we whichever happens first for the last sector erase command pulse and terminates when the data on dq 7 is 1 (see 12. write operation status.) at which time the device return to the read mode. data polling and toggle bit must be performed at an address within any of the sectors being erased. multiple sector erase time; [sector erase time + sector program time (preprogramming) ] number of sector erase 2. embedded erase tm algorithm in n flow chart illustrates the embedded erase tm algorithm using typical command strings and bus operations. 6. erase suspend/resume the erase suspend command allows the user to interrupt a sector erase operation and then perform data reads from or programs to a sector not being erased. this command is applicable only during the sector erase operation which includes the time-out period for sector erase. the erase suspend command will be ignored if written during the chip erase operation or embedded program algorithm. writting the erase suspend command (b0h) during the sector erase time-out results in immediate termination of the time-out period and suspension of the erase operation. writing the erase resume command (30h) resumes the erase operation. the addresses are dont cares when writing the erase suspend or erase resume command. when the erase suspend command is written during the sector erase operation, the device will take a maximum of t spd to suspend the erase operation. when the device has entered the erase-suspended mode, the ry/by output pin will be at hi-z and the dq 7 bit will be at logic 1, and dq 6 will stop toggling. the user must use the address of the erasing sector for reading dq 6 and dq 7 to determine if the erase operation has been suspended. further writes of the erase suspend command are ignored. when the erase operation has been suspended, the device defaults to the erase-suspend-read mode. reading data in this mode is the same as reading from the standard read mode except that the data must be read from sectors that have not been erase-suspended. successively reading from the erase-suspended sector while the device is in the erase-suspend-read mode will cause dq 2 to toggle. (see 17. dq 2 .) after entering the erase-suspend-read mode, the user can program the device by writing the appropriate com- mand sequence for program. this program mode is known as the erase-suspend-program mode. again, pro- gramming in this mode is the same as programming in the regular program mode except that the data must be programmed to sectors that are not erase-suspended. successively reading from the erase-suspended sector while the device is in the erase-suspend-program mode will cause dq 2 to toggle. the end of the erase-suspended program operation is detected by the ry/by output pin, data polling of dq 7 or by the toggle bit i (dq 6 ) which is the same as the regular program operation. note that dq 7 must be read from the program address while dq 6 can be read from any address. to resume the operation of sector erase, the resume command (30h) should be written. any further writes of the resume command at this point will be ignored. another erase suspend command can be written after the chip has resumed erasing. 7. extended command (1) fast mode the device has fast mode function. this mode dispenses with the initial two unclock cycles required in the standard program command sequence by writing fast mode command into the command register. in this mode, the required bus cycle for programming is two cycles instead of four bus cycles in standard program command. (do not write erase command in this mode.) the read operation is also executed after exiting this mode. to exit this mode, it is necessary to write fast mode reset command into the command register. (see 8. embedded program tm algorithm for fast mode in n flow chart .) the v cc active current is required even ce = v ih during fast mode.
mbm29lv320te/be 80/90/10 29 (2) fast programming during fast mode, the programming can be executed with two bus cycles operation. the embedded program algorithm is executed by writing program set-up command (a0h) and data write cycles (pa/pd) . (see 8. embedded program tm algorithm for fast mode in n flow chart.) (3) cfi (common flash memory interface) the cfi (common flash memory interface) specification outlines device and host system software interrogation handshake which allows specific vendor-specified software algorithms to be used for entire families of device. this allows device-independent, jedec id-independent, and forward-and backward-compatible software sup- port for the specified flash device families. see common flash memory interface code table in n flexible sector-erase architecture for details. the operation is initiated by writing the query command (98h) into the command register. following the command write, a read cycle from specific address retrives device information. please note that output data of upper byte (dq 15 to dq 8 ) is 0 in word mode (16 bit) read. see common flash memory interface code table in n flexible sector-erase architecture. to terminate operation, it is necessary to write the read/reset command sequence into the register. (see common flash memory interface code table in n flexible sector- erase architecture.) 8. hidden rom (hi-rom) region the hi-rom feature provides a flash memory region that the system may access through a new command sequence. this is primarily intended for customers who wish to use an electronic serial number (esn) in the device with the esn protected against modification. once the hi-rom region is protected, any further modifi- cation of that region is impossible. this ensures the security of the esn once the product is shipped to the field. the hi-rom region is 256 bytes in length and is stored at the same address of the outermost 8 k byte boot sector. the mbm29lv320te occupies the address of the byte mode 3fffc0h to 3fffffh (word mode 1fffe0h to 1fffffh) and the mbm29lv320be type occupies the address of the byte mode 000000h to 000080h (word mode 000000h to 000040h) . after the system has written the enter hi-rom command sequence, the system may read the hi-rom region by using the addresses normally occupied by the boot sector. that is, the device sends all commands that would normally be sent to the boot sector to the hi-rom region. this mode of operation continues until the system issues the exit hi-rom command sequence, or until power is removed from the device. on power-up, or following a hardware reset, the device reverts to sending commands to the boot sector. 9. hidden rom (hi-rom) entry command the device has a hidden rom area with one time protect function. this area is to enter the security code and to unable the change of the code once set. program/erase is possible in this area until it is protected. however, once it is protected, it is impossible to unprotect, so please use this with caution. hidden rom area is 256 byte and in the same address area of outermost 8 k byte boot block. therefore, write the hidden rom entry command sequence to enter the hidden rom area. it is called as hidden rom mode when the hidden rom area appears. sector other than the boot block area could be read during hidden rom mode. read/program of the hidden rom area is possible during hidden rom mode. write the hidden rom reset command sequence to exit the hidden rom mode. 10. hidden rom (hi-rom) program command to program the data to the hidden rom area, write the hidden rom program command sequence during hidden rom mode. this command is the same as the program command in usual except to write the command during hidden rom mode. therefore the detection of completion method is the same as in the past, using the dq 7 data poling, dq 6 toggle bit and ry/by pin. need to pay attention to the address to be programmed. if the address other than the hidden rom area is selected to program, data of the address will be changed. please note that the sector erase command is prohibited during hidden rom mode. if the sector erase command is appeared in this mode, data of the address will be erased.
mbm29lv320te/be 80/90/10 30 11. hidden rom (hi-rom) protect command there are two methods to protect the hidden rom area. one is to write the sector group protect setup command (60h) , set the sector address in the hidden rom area and (a 6 , a 1 , a 0 ) = (0,1,0) , and write the sector group protect command (60h) during the hidden rom mode. the same command sequence could be used because it is the same as the extension sector group protect in the past except that it is in the hidden rom mode and it does not apply high voltage to reset pin. please see 9. extended sector group protection in n functional description for details of extention sector group protect setting. the other is to apply high voltage (v id ) to a 9 and oe , set the sector address in the hidden rom area and (a 6 , a 1 , a 0 ) = (0,1,0) , and apply the write pulse during the hidden rom mode. to verify the protect circuit, apply high voltage (v id ) to a 9 , specify (a 6 , a 1 , a 0 ) = (0,1,0) and the sector address in the hidden rom area, and read. when 1 appears on dq 0 , the protect setting is completed. 0 will appear on dq 0 if it is not protected. please apply write pulse agian. the same command sequence could be used for the above method because other than the hidden rom mode, it is the same as the sector group protect in the past. please see 7. sector group protection in n functional description for details of the sector group protect setting. other sector group will be effected if the address other than those for hidden rom area is selected for the sector group address, so please be carefull. once it is protected, protection can not be cancelled, so please pay the closest attention. 12. write operation status details in hardware sequence flags table are all the status flags that can be used to check the status of the device for current mode operation. during sector erase, the part provides the status flags automatically to the i/o ports. the information on dq 2 is address sensitive. this means that if an address from an erasing sector is consecutively read, then the dq 2 bit will toggle. however, dq 2 will not toggle if an address from a non-erasing sector is consecutively read. this allows users to determine which sectors are in erase. once erase suspend is entered, address sensitivity still applies. if the address of a non-erasing sector (that is, one available for read) is provided, then stored data can be read from the device. if the address of an erasing sector (that is, one unavailable for read) is applied, the device will output its status bits. hardware sequence flags table *: successive reads from the erasing or erase-suspend sector will cause dq 2 to toggle. reading from non-erase suspend sector address will indicate logic 1 at the dq 2 bit. status dq 7 dq 6 dq 5 dq 3 dq 2 in progress embedded program algorithm dq 7 toggle 0 0 1 embedded erase algorithm 0 toggle 0 1 toggle * erase suspended mode erase suspend read (erase suspended sector) 1100toggle erase suspend read (non-erase suspended sector) data data data data data erase suspend program (non-erase suspended sector) dq 7 toggle 0 0 1 * exceeded time limits embedded program algorithm dq 7 toggle 1 0 1 embedded erase algorithm 0 toggle 1 1 n/a erase suspended mode erase suspend program (non-erase suspended sector) dq 7 toggle 1 0 n/a
mbm29lv320te/be 80/90/10 31 13. dq 7 data polling the device features data polling as a method to indicate to the host that the embedded algorithms are in progress or completed. during the embedded program algorithm an attempt to read the device will produce a complement of data last written to dq 7 . upon completion of the embedded program algorithm, an attempt to read device will produce true data last written to dq 7 . during the embedded erase algorithm, an attempt to read device will produce a 0 at the dq 7 output. upon completion of the embedded erase algorithm an attempt to read device will produce a 1 on dq 7 . the flowchart for data polling (dq 7 ) is shown in 3. data polling algorithm ( n flow chart). for programming, the data polling is valid after the rising edge of the fourth write pulse in the four write pulse sequence. for chip erase and sector erase, the data polling is valid after the rising edge of the sixth write pulse in the six write pulse sequence. data polling must be performed at sector address within any of the sectors being erased, not a protected sectors. otherwise, the status may be invalid. once the embedded algorithm operation is close to being completed, the device data pins (dq 7 ) may change asynchronously while the output enable (oe ) is asserted low. this means that the device is driving status information on dq 7 at one instant of time and then that bytes valid data at the next instant of time. depending on when the system samples the dq 7 output, it may read the status or valid data. even if the device has completed the embedded algorithm operation and dq 7 has a valid data, the data outputs on dq 0 to dq 6 may be still invalid. the valid data on dq 0 to dq 7 will be read on the successive read attempts. the data polling feature is active only during the embedded programming algorithm, embedded erase algo- rithm, erase suspend mode or sector erase time-out. (see hardware sequence flags table.) see 6. data polling during embedded algorithm operation timing diagram in n timing diagram for the data polling timing specifications and diagrams. 14. dq 6 toggle bit i the device also features the toggle bit i as a method to indicate to the host system that the embedded algorithms are in progress or completed. during embedded program or erase algorithm cycle, successive attempts to read (ce or oe toggling) data from the device will results in dq 6 toggling between one and zero. once the embedded program or erase algorithm cycle is completed, dq 6 will stop toggling and valid data will be read on the next successive attempts. during programming, the toggle bit i is valid after the rising edge of the fourth write pulse in the four write pulse sequence. for chip erase and sector erase, the toggle bit i is valid after the rising edge of the sixth write pulse in the six write pulse sequence. the toggle bit i is active during the sector time out. in program operation, if the sector being written is protected, the toggle bit will toggle for about 1 m s and then stop toggling with data unchanged. in erase operation, the device will erase all selected sectors except for ones that are protected. if all selected sectors are protected, chip will toggle the toggle bit for about 400 m s and then drop back into read mode, having data unchanged. either ce or oe toggling will cause dq 6 to toggle. see 7. toggle bit i during embedded algorithm operation timing diagram in n timing diagram for the toggle bit i timing specifications and diagrams. 15. dq 5 exceeded timing limits dq 5 will indicate if the program or erase time has exceeded the specified limits (internal pulse count) . under these conditions dq 5 will produce a 1. this is a failure condition which indicates that the program or erase cycle was not successfully completed. data polling is the only operating function of device under this condition. the ce circuit will partially power down device under these conditions (to approximately 2 ma) . the oe and
mbm29lv320te/be 80/90/10 32 we pins will control the output disable functions as described in mbm29lv320te/be user bus operations ta b l e s ( b y t e = v ih and byte = v il ) ( n device bus operations). the dq 5 failure condition may also appear if a user tries to program a non blank location without erasing. in this case the device locks out and never complete the embedded algorithm operation. hence, the system never read valid data on dq 7 bit and dq 6 never stop toggling. once the device has exceeded timing limits, the dq 5 bit will indicate a 1. please note that this is not a device failure condition since device was incorrectly used. if this occurs, reset device with command sequence. 16. dq 3 sector erase timer after completion of the initial sector erase command sequence the sector erase time-out will begin. dq 3 will remain low until the time-out is completed. data polling and toggle bit are valid after the initial sector erase command sequence. if data polling or toggle bit i indicates device has been written with a valid erase command, dq 3 may be used to determine if the sector erase timer window is still open. if dq 3 is high (1) the internally controlled erase cycle has begun; attempts to write subsequent commands to the device will be ignored until the erase operation is completed as indicated by data polling or toggle bit i. if dq 3 is low (0) , the device will accept additional sector erase commands. to insure the command has been accepted, the system software should check the status of dq 3 prior to and following each subsequent sector erase command. if dq 3 were high on the second status check, the command may not have been accepted. see hardware sequence flags table. 17. dq 2 toggle bit ii this toggle bit ii, along with dq 6 , can be used to determine whether the device is in the embedded erase algorithm or in erase suspend. successive reads from the erasing sector will cause dq 2 to toggle during the embedded erase algorithm. if the device is in the erase-suspended-read mode, successive reads from the erase-suspended sector will cause dq 2 to toggle. when the device is in the erase-suspended-program mode, successive reads from the byte address of the non-erase suspended sector will indicate a logic 1 at the dq 2 bit. dq 6 is different from dq 2 in that dq 6 toggles only when the standard program or erase, or erase suspend program operation is in progress. the behavior of these two status bits, along with that of dq 7 , is summarized as follows : for example, dq 2 and dq 6 can be used together to determine if the erase-suspend-read mode is in progress. (dq 2 toggles while dq 6 does not.) see also toggle bit status table and 8. dq 2 vs dq 6 in n timing diagram. furthermore, dq 2 can also be used to determine which sector is being erased. when the device is in the erase mode, dq 2 toggles if this bit is read from an erasing sector. 18. reading toggle bits dq 6 /dq 2 whenever the system initially begins reading toggle bit status, it must read dq 7 to dq 0 at least twice in a row to determine whether a toggle bit is toggling. typically, a system would note and store the value of the toggle bit after the first read. after the second read, the system would compare the new value of the toggle bit with the first. if the toggle bit is not toggling, this indicates that the device has completed the program or erase operation. the system can read array data on dq 7 to dq 0 on the following read cycle. however, if after the initial two read cycles, the system determines that the toggle bit is still toggling, the system also should note whether the value of dq 5 is high (see 15. dq 5 ) . if it is the system should then determine again whether the toggle bit is toggling, since the toggle bit may have stopped toggling just as dq 5 went high. if the toggle bit is no longer toggling, the device has successfully completed the program or erase operation. if it is still toggling, the device did not complete the operation successfully, and the system must write the reset command to return to reading array data.
mbm29lv320te/be 80/90/10 33 the remaining scenario is that the system initially determines that the toggle bit is toggling and dq 5 has not gone high. the system may continue to monitor the toggle bit and dq 5 through successive read cycles, deter- mining the status as described in the previous paragraph. alternatively, it may choose to perform other system tasks. in this case, the system must start at the beginning of the algorithm when it returns to determine the status of the operation. (see 4. toggle bit algorithm in n flow chart.) toggle bit status table * : successive reads from the erasing or erase-suspend sector will cause dq 2 to toggle. reading from non-erase suspend sector address will indicate logic 1 at the dq 2 bit. 19. ry/by ready/busy the device provides a ry/by open-drain output pin as a way to indicate to the host system that the embedded algorithms are either in progress or has been completed. if output is low, the device is busy with either a program or erase operation. if output is high, the device is ready to accept any read/write or erase operation. when the ry/by pin is low, the device will not accept any additional program or erase commands. if the device is placed in an erase suspend mode, ry/by output will be high. during programming, ry/by pin is driven low after the rising edge of the fourth write pulse. during an erase operation, ry/by pin is driven low after the rising edge of the sixth write pulse. ry/by pin will indicate a busy condition during reset pulse. see 9. ry/by timing diagram during program/erase operations and 10. reset , ry/by timing diagram in n timing diagram for a detailed timing diagram. ry/by pin is pulled high in standby mode. since this is an open-drain output, ry/by pins can be tied together in parallel with a pull-up resistor to v cc . 20. byte/word configuration byte pin selects byte (8-bit) mode or word (16-bit) mode for device. when this pin is driven high, the device operates in word (16-bit) mode. data is read and programmed at dq 15 to dq 0 . when this pin is driven low, the device operates in byte (8-bit) mode. under this mode, dq 15 /a -1 pin becomes the lowest address bit, and dq 14 to dq 8 bits are tri-stated. however, the command bus cycle is always an 8-bit operation and hence commands are written at dq 15 to dq 8 and the dq 7 to dq 0 bits are ignored. see 11. word mode configuration timing diagram, 12. byte mode configuration timing diagram and 13. byte timing diagram for write operations in n timing diagram the detail . 21. data protection the device is designed to offer protection against accidental erasure or programming caused by spurious system level signals that may exist during power transitions. during power up device automatically resets internal state machine in read mode. also, with its control register architecture, alteration of memory contents only occurs after successful completion of specific multi-bus cycle command sequences. the device also incorporates several features to prevent inadvertent write cycles resulting from v cc power-up and power-down transitions or system noise. mode dq 7 dq 6 dq 2 program dq 7 toggle 1 erase 0 toggle toggle* erase-suspend read (erase-suspended sector) 11toggle erase-suspend program dq 7 toggle 1*
mbm29lv320te/be 80/90/10 34 22. low v cc write inhibit to avoid initiation of a write cycle during v cc power-up and power-down, a write cycle is locked out for v cc less than v lko (min) . if v cc < v lko , the command register is disabled and all internal program/erase circuits are disabled. under this condition the device will reset to the read mode. subsequent writes will be ignored until the v cc level is greater than v lko . it is the users responsibility to ensure that the control pins are logically correct to prevent unintentional writes when v cc is above v lko (min) . if embedded erase algorithm is interrupted, there is possibility that the erasing sector (s) cannot be used. 23. write pulse glitch protection noise pulses of less than 3 ns (typ) on oe , ce , or we will not initiate a write cycle. 24. logical inhibit writing is inhibited by holding any one of oe = v il , ce = v ih , or we = v ih . to initiate a write cycle ce and we must be a logical zero while oe is a logical one. 25. power-up write inhibit power-up of the device with we = ce = v il and oe = v ih will not accept commands on the rising edge of we . the internal state machine is automatically reset to the read mode on power-up.
mbm29lv320te/be 80/90/10 35 n n n n absolute maximum ratings *1 : voltage is defined on the basis of v ss = gnd = 0 v. *2 : minimum dc voltage on input or l/o pins is - 0.5 v. during voltage transitions, input or i/o pins may undershoot v ss to - 2.0 v for periods of up to 20 ns. maximum dc voltage on input or l/o pins is v cc + 0.5 v. during voltage transitions, input or i/o pins may overshoot to v cc + 2.0 v for periods of up to 20 ns. * 3: minimum dc input voltage on a 9 , oe and reset pins is - 0.5 v. during voltage transitions, a 9 , oe and reset pins may undershoot v ss to - 2.0 v for periods of up to 20 ns. voltage difference between input and supply voltage (v in - v cc ) does not exceed + 9.0 v.maximum dc input voltage on a 9 , oe and reset pins is + 13.0 v which may overshoot to + 14.0 v for periods of up to 20 ns. * 4: minimum dc input voltage on wp /acc pin is - 0.5 v. during voltage transitions, wp /acc pin may undershoot v ss to - 2.0 v for periods of up to 20 ns. maximum dc input voltage on wp /acc pin is + 13.0 v which may overshoot to + 12.0 v for periods of up to 20 ns when v cc is applied. warning: semiconductor devices can be permanently damaged by application of stress (voltage, current, temperature, etc.) in excess of absolute maximum ratings. do not exceed these ratings. n n n n recommended operating ranges operating ranges define those limits between which the functionality of the device is guaranteed. warning: the recommended operating conditions are required in order to ensure the normal operation of the semiconductor device. all of the devices electrical characteristics are warranted when the device is operated within these ranges. always use semiconductor devices within their recommended operating condition ranges. operation outside these ranges may adversely affect reliability and could result in device failure. no warranty is made with respect to uses, operating conditions, or combinations not represented on the data sheet. users considering application outside the listed conditions are advised to contact their fujitsu representatives beforehand. parameter symbol rating unit min max storage temperature tstg - 55 + 125 c ambient temperature with power applied t a - 40 + 85 c voltage with respect to ground all pins except a 9 , oe , and reset * 1, * 2 v in , v out - 0.5 v cc + 0.5 v power supply voltage * 1 v cc - 0.5 + 4.0 v a 9 , oe , and reset * 1, * 3 v in - 0.5 + 13.0 v wp /acc * 1, * 4 v acc - 0.5 + 13.0 v parameter symbol part no. value unit min max ambient temperature t a mbm29lv320te/be 80/90/10 - 40 + 85 c power supply voltage v cc mbm29lv320te/be 80/90 + 3.0 + 3.6 v mbm29lv320te/be 10 + 2.7 + 3.6
mbm29lv320te/be 80/90/10 36 n maximum overshoot/undershoot + 0.6 v - 0.5 v 20 ns - 2.0 v 20 ns 20 ns maximum undershoot waveform v cc + 0.5 v v cc + 2.0 v + 2.0 v 20 ns 20 ns 20 ns maximum overshoot waveform 1 + 13.0 v v cc + 0.5 v + 14.0 v 20 ns 20 ns 20 ns note : this waveform is applied for a 9 , oe, and reset. maximum overshoot waveform 2
mbm29lv320te/be 80/90/10 37 n n n n dc characteristics * 1: the i cc current listed includes both the dc operating current and the frequency dependent component. * 2: i cc active while embedded algorithm (program or erase) is in progress. * 3: automatic sleep mode enables the low power mode when addresses remain stable for 150 ns. * 4: applicable for only v cc applying. parameter symbol conditions min max unit input leakage current i li v in = v ss to v cc , v cc = v cc max - 1.0 + 1.0 m a output leakage current i lo v out = v ss to v cc , v cc = v cc max - 1.0 + 1.0 m a a 9 , oe , reset inputs leakage current i lit v cc = v cc max, a 9 , oe , reset = 12.5 v ? 35 m a v cc active current * 1 i cc1 ce = v il , oe = v ih , f = 5 mhz byte ? 16 ma word 18 ce = v il , oe = v ih , f = 1 mhz byte ? 7 ma word 7 v cc active current * 2 i cc2 ce = v il , oe = v ih ? 40 ma v cc current (standby) i cc3 v cc = v cc max, ce = v cc 0.3 v, reset = v cc 0.3 v ? 5 m a v cc current (standby, reset) i cc4 v cc = v cc max,we /acc = v cc 0.3 v, reset = v ss 0.3 v ? 5 m a v cc current (automatic sleep mode) * 3 i cc5 v cc = v cc max, ce = v ss 0.3 v, reset = v cc 0.3 v v in = v cc 0.3 v or v ss 0.3 v ? 5 m a wp /acc accelerated program current i acc v cc = v cc max, wp /acc = v acc max ? 20 ma input low level v il ?- 0.5 + 0.6 v input high level v ih ? 2.0 v cc + 0.3 v voltage for wp /acc sector protection/unprotection and program acceleration v acc ? 11.5 12.5 v voltage for autoselect and sector group protection (a 9 , oe , reset ) * 4 v id ? 11.5 12.5 v output low voltage level v ol i ol = 4.0 ma, v cc = v cc min ? 0.45 v output high voltage level v oh1 i oh = - 2.0 ma, v cc = v cc min 2.4 ? v v oh2 i oh = - 100 m av cc - 0.4 ? v low v cc lock-out voltage v lko ? 2.3 2.5 v
mbm29lv320te/be 80/90/10 38 n ac characteristics ? read only operations characteristics * : test conditions : output load : 1 ttl gate and 30 pf (mbm29lv320te80, mbm29lv320be80) 100 pf (mbm29lv320te90/10, mbm29lv320be90/10) input rise and fall times : 5 ns input pulse levels : 0.0 v or 3.0 v timing measurement reference level input : 1.5 v output : 1.5 v parameter symbol condi- tion value unit jedec standard 80 * 90* 10* min max min max min max read cycle time t avav t rc ? 80 ? 90 100 ? ns address to output delay t avqv t acc ce = v il oe = v il ? 80 ? 90 ? 100 ns chip enable to output delay t elqv t ce oe = v il ? 80 ? 90 ? 100 ns output enable to output delay t glqv t oe ?? 30 ? 35 ? 35 ns chip enable to output high-z t ehqz t df ?? 25 ? 30 ? 30 ns output enable to output high-z t ghqz t df ?? 25 ? 30 ? 30 ns output hold time from addresses, ce or oe , whichever occurs first t axqx t oh ? 0 ? 0 ? 0 ? ns reset pin low to read mode ? t ready ?? 20 ? 20 ? 20 m s ce to byte switching low or high ? t elfl t elfh ?? 5 ? 5 ? 5ns c l 3.3 v diodes = in3064 or equivalent 2.7 k w device under test in3064 or equivalent 6.2 k w notes : c l = 30 pf including jig capacitance (mbm29lv320te80, mbm29lv320be80) c l = 100 pf including jig capacitance (mbm29lv320te90/10, mbm29lv320be90/10) test conditions
mbm29lv320te/be 80/90/10 39 ? write/erase/program operations (continued) parameter symbol value unit jedec standard 80 (note) 90 (note) 10 (note) min typ max min typ max min typ max write cycle time t avav t wc 80 ?? 90 ?? 100 ?? ns address setup time t avwl t as 0 ?? 0 ?? 0 ?? ns address hold time t wlax t ah 45 ?? 45 ?? 45 ?? ns data setup time t dvwh t ds 30 ?? 35 ?? 35 ?? ns data hold time t whdx t dh 0 ?? 0 ?? 0 ?? ns output en- able hold time read ? t oeh 0 ?? 0 ?? 0 ?? ns toggle and data polling 10 ?? 10 ?? 10 ?? ns read recover time before write t ghwl t ghwl 0 ?? 0 ?? 0 ?? ns read recover time before write (oe high to ce low) t ghel t ghel 0 ?? 0 ?? 0 ?? ns ce setup time t elwl t cs 0 ?? 0 ?? 0 ?? ns we setup time t wlel t ws 0 ?? 0 ?? 0 ?? ns ce hold time t wheh t ch 0 ?? 0 ?? 0 ?? ns we hold time t ehwh t wh 0 ?? 0 ?? 0 ?? ns write pulse width t wlwh t wp 35 ?? 35 ?? 35 ?? ns ce pulse width t eleh t cp 35 ?? 35 ?? 35 ?? ns write pulse width high t whwl t wph 25 ?? 30 ?? 30 ?? ns ce pulse width high t ehel t cph 25 ?? 30 ?? 30 ?? ns programming operation byte t whwh1 t whwh1 ? 8 ?? 8 ?? 8 ?m s word ? 16 ?? 16 ?? 16 ?m s sector erase operation * 1 t whwh2 t whwh2 ? 1 ?? 1 ?? 1 ? s v cc setup time ? t vcs 50 ?? 50 ?? 50 ?? m s rise time to v id * 2 ? t vidr 500 ?? 500 ?? 500 ?? ns rise time to v acc * 3 ? t vaccr 500 ?? 500 ?? 500 ?? ns voltage transition time * 2 ? t vlht 4 ?? 4 ?? 4 ?? m s write pulse width * 2 ? t wpp 100 ?? 100 ?? 100 ?? m s oe setup time to we active * 2 ? t oesp 4 ?? 4 ?? 4 ?? m s ce setup time to we active * 2 ? t csp 4 ?? 4 ?? 4 ?? m s recover time from ry/by ? t rb 0 ?? 0 ?? 0 ?? ns reset pulse width ? t rp 500 ?? 500 ?? 500 ?? ns reset high level period before read ? t rh 200 ?? 200 ?? 200 ?? ns
mbm29lv320te/be 80/90/10 40 (continued) *1 : this does not include the preprogramming time. *2 : this timing is for sector group protection operation. *3 : this timing is limited for accelerated program operation only. parameter symbol value unit jedec standard 80 (note) 90 (note) 10 (note) min typ max min typ max min typ max byte switching low to output high-z ? t flqz ?? 30 ?? 30 ?? 30 ns byte switching high to output active ? t fhqv ?? 80 ?? 90 ?? 100 ns program/erase valid to ry/by delay ? t busy ?? 90 ?? 90 ?? 90 ns delay time from embedded output enable ? t eoe ?? 80 ?? 90 ?? 100 ns erase time-out time ? t tow 50 ?? 50 ?? 50 ?? m s erase suspend transition time ? t spd ?? 20 ?? 20 ?? 20 m s
mbm29lv320te/be 80/90/10 41 n erase and programming performance n tsop (i) pin capacitance note : test conditions t a = + 25 c, f = 1.0 mhz n fbga pin capacitance note : test conditions t a = + 25 c, f = 1.0 mhz parameter limits unit comments min typ max sector erase time ? 110s excludes programming time prior to erasure word programming time ? 16 360 m s excludes system-level over- head byte programming time ? 8 300 m s chip programming time ?? 100 s excludes system-level over- head program/erase cycle 100,000 ?? cycle ? parameter symbol condition value unit typ max input capacitance c in v in = 06.07.5pf output capacitance c out v out = 0 8.5 12.0 pf control pin capacitance c in2 v in = 0 8.0 10.0 pf wp /acc pin capacitance c in3 v in = 0 15.0 20.0 pf parameter symbol condition value unit typ max input capacitance c in v in = 06.07.5pf output capacitance c out v out = 0 8.5 12.0 pf control pin capacitance c in2 v in = 0 8.0 10.0 pf wp /acc pin capacitance c in3 v in = 0 15.0 20.0 pf
mbm29lv320te/be 80/90/10 42 n timing diagram ? key to switching waveforms 1. read operation timing diagram waveform inputs outputs must be steady may change from h to l may change from l to h "h" or "l" any change permitted does not apply will be steady will change from h to l will change from l to h changing state unknown center line is high- impedance "off" state address address stable high-z high-z ce oe we outputs output valid t rc t acc t oe t df t ce t oh t oeh
mbm29lv320te/be 80/90/10 43 2. hardware reset/read operation timing diagram 3. alternate we controlled program operation timing diagram address ce reset outputs high-z output valid address stable t rc t acc t rh t rp t rh t ce t oh address data ce oe we 3rd bus cycle data polling 555h pa a0h pd dq 7 d out d out pa t wc t as t ah t rc t ce t whwh1 t wph t wp t ghwl t ds t dh t oh t oe t cs t ch notes : pa is address of the memory location to be programmed. pd is data to be programmed at byte address. dq 7 is the output of the complement of the data written to the device. d out is the output of the data written to the device. figure indicates last two bus cycles out of four bus cycle sequence. these waveforms are for the 16 mode. (the addresses differ from 8 mode.)
mbm29lv320te/be 80/90/10 44 4. alternate ce controlled program operation timing diagram address data we oe ce 3rd bus cycle data polling 555h pa a0h pd dq 7 d out pa t wc t as t ah t whwh1 t cph t cp t ghel t ds t dh t ws t wh notes : pa is address of the memory location to be programmed. pd is data to be programmed at byte address. dq 7 is the output of the complement of the data written to the device. d out is the output of the data written to the device. figure indicates last two bus cycles out of four bus cycle sequence. these waveforms are for the 16 mode. (the addresses differ from 8 mode.)
mbm29lv320te/be 80/90/10 45 5. chip/sector erase operation timing diagram address data v cc ce oe we 555h 2aah 555h 555h 2aah sa* t wc t as t ah t cs t ghwl t ch t wp t ds t vcs t dh t wph aah 55h 80h aah 55h 30h 10h for chip erase * : sa is the sector address for sector erase. addresses = 555h (word), aaah (byte) for chip erase. note : these waveforms are for the 16 mode. (the addresses differ from 8 mode.)
mbm29lv320te/be 80/90/10 46 6. data polling during embedded algorithm operation timing diagram 7. toggle bit i during embedded algorithm operation timing diagram t oeh t ch t oe t ce t df t busy t eoe t whwh1 or 2 ce dq 7 dq 6 to dq 0 ry/by dq 7 dq 7 = valid data dq 6 to dq 0 = output flag dq 6 to dq 0 valid data oe we high-z high-z data data * * : dq 7 = valid data (the device has completed the embedded operation) . t oeh ce we oe dq 6 t oe t dh data (dq 0 to dq 7 ) dq 6 = toggle dq 6 = stop toggling dq 6 = toggle dq 0 to dq 7 data valid * * : dq 6 = stops toggling. (the device has completed the embedded operation.)
mbm29lv320te/be 80/90/10 47 8. dq 2 vs. dq 6 9. ry/by timing diagram during program/erase operations 10. reset , ry/by timing diagram enter embedded erasing erase suspend erase resume enter erase suspend program erase suspend program erase complete erase erase suspend read erase suspend read erase dq 6 dq 2 * we toggle dq 2 and dq 6 with oe or ce * : dq 2 is read from the erase-suspended sector. ce ry/by we rising edge of the last write pulse t busy entire programming or erase operations t rp t rb t ready ry/by we reset
mbm29lv320te/be 80/90/10 48 11. word mode configuration timing diagram 12. byte mode configuration timing diagram 13. byte timing diagram for write operations t ce t fhqv t elfh a -1 data output (dq 7 to dq 0 ) data output (dq 14 to dq 0 ) dq 15 ce byte dq 14 to dq 0 dq 15 /a -1 t elfl t acc t flqz a -1 data output (dq 14 to dq 0 ) data output (dq 7 to dq 0 ) dq 15 ce byte dq 14 to dq 0 dq 15 /a -1 t set (t as ) t hold (t ah ) ce or we byte input valid falling edge of last write signal
mbm29lv320te/be 80/90/10 49 14. sector group protection timing diagram t wpp t vlht t vlht t oe t csp t oesp t vcs t vlht t vlht a 20 , a 19 , a 18 a 17 , a 16 , a 15 a 14 , a 13 , a 12 a 6 , a 0 a 1 a 9 v cc oe v id 3 v v id 3 v we ce data spax 01h spay spax : sector group address to be protected. spay : next sector group address to be protected. note : a -1 is v il on byte mode.
mbm29lv320te/be 80/90/10 50 15. temporary sector group unprotection timing diagram unprotection period t vlht t vlht t vcs t vlht t vidr program or erase command sequence v cc v id 3 v we ry/by ce reset
mbm29lv320te/be 80/90/10 51 16. extended sector group protection timing diagram v cc we oe ce reset t wc t wc t vlht t vidr t vcs time-out spax spax spay t wp t oe 60h 01h 40h 60h 60h data address a 6 , a 0 a 1 spax : sector group address to be protected spay : next sector group address to be protected time-out : time-out window = 250 m s (min)
mbm29lv320te/be 80/90/10 52 17. accelerated program timing diagram 3 v wp/acc v cc ce we ry/by t vlht t vlht t vcs t vaccr v acc t vlht program command sequence acceleration period
mbm29lv320te/be 80/90/10 53 n flow chart 1. embedded program tm algorithm 555h/aah 555h/a0h 2aah/55h program address/program data programming completed last address ? increment address verify data ? data polling program command sequence (address/command) : write program command sequence (see below) start no no yes yes embedded program algorithm in progress note : the sequence is applied for 16 mode. the addresses differ from 8 mode. embedded algorithm
mbm29lv320te/be 80/90/10 54 2. embedded erase tm algorithm 555h/aah 555h/80h 2aah/55h 555h/aah 555h/10h 2aah/55h 555h/aah 555h/80h 2aah/55h 555h/aah sector address /30h sector address /30h sector address /30h 2aah/55h erasure completed data = ffh ? data polling write erase command sequence (see below) start no yes embedded erase algorithm in progress chip erase command sequence (address/command) : individual sector/multiple sector erase command sequence (address/command) : additional sector erase commands are optional. note : the sequence is applied for 16 mode. the addresses differ from 8 mode. embedded algorithm
mbm29lv320te/be 80/90/10 55 3. data polling algorithm dq 7 = data? dq 5 = 1? fail pass dq 7 = data? * read byte (dq 7 to dq 0 ) addr. = va read byte (dq 7 to dq 0 ) addr. = va start no no no yes yes yes * : dq 7 is rechecked even if dq 5 = 1 because dq 7 may change simultaneously with dq 5 . va = address for programming = any of the sector addresses within the sector being erased during sector erase or multiple erases operation = any of the sector addresses within the sector not being protected during sector erase or multiple sector erases operation
mbm29lv320te/be 80/90/10 56 4. toggle bit algorithm dq 6 = toggle? dq 5 = 1? dq 6 = toggle? read dq 7 to dq 0 addr. = "h" or "l" read dq 7 to dq 0 addr. = "h" or "l" read dq 7 to dq 0 twice addr. = "h" or "l" start no no no yes yes yes program/erase operation not complete, write reset command program/erase operation complete *1 *1, *2 *1 : read toggle bit twice to determine whether or not it is toggling. *2 : recheck toggle bit because it may stop toggling as dq 5 changes to 1.
mbm29lv320te/be 80/90/10 57 5. sector group protection algorithm start no no no yes yes yes data = 01h? device failed plscnt = 25? plscnt = 1 remove v id from a 9 write reset command remove v id from a 9 write reset command sector group protection completed protect another sector group ? increment plscnt read from sector group addr. = spa, a 1 = v ih a 6 = a 0 = v il setup sector group addr. a 20 , a 19 , a 18 , a 17 ,a 16 , a 15 , a 14 , a 13 , a 12 oe = v id , a 9 = v id , ce = v il , reset = v ih a 6 = a 0 = v il , a 1 = v ih activate we pulse time out 100 m s we = v ih , ce = oe = v il (a 9 should remain v id ) () () * * : a -1 is v il on byte mode.
mbm29lv320te/be 80/90/10 58 6. temporary sector group unprotection algorithm start perform erase or program operations reset = v id *1 temporary sector group unprotection completed *2 reset = v ih *1 : all protected sectors are unprotected. *2 : all previously protected sectors are protected once again.
mbm29lv320te/be 80/90/10 59 7. extended sector group protection algorithm start no yes yes data = 01h? plscnt = 1 no no yes device failed plscnt = 25? remove v id from reset write reset command sector group protection completed protection other sector group ? increment plscnt read from sector group address (a 0 = v il , a 1 = v ih , a 6 = v il ) remove v id from reset write reset command time out 250 m s reset = v id wait to 4 m s no yes setup next sector address device is operating in temporary sector group unprotection mode to protect sector group write 60h to sector address (a 6 = a 0 = v il , a 1 = v ih ) to verify sector group protection write 40h to sector address (a 6 = a 0 = v il , a 1 = v ih ) to setup sector group protection write xxxh/60h extended sector group protection entry?
mbm29lv320te/be 80/90/10 60 8. embedded program tm algorithm for fast mode 555h/aah 555h/20h xxxxh/90h xxxxh/f0h xxxh/a0h 2aah/55h program address/program data programming completed last address ? increment address verify data? data polling start no no yes yes set fast mode in fast program reset fast mode notes : the sequence is applied for 16 mode. the addresses differ from 8 mode. fast mode algorithm
mbm29lv320te/be 80/90/10 61 n ordering information standard products fujitsu standard products are available in several packages. the order number is formed by a combination of : mbm29lv320 t e 80 tn package type tn = 48-pin thin small outline package (tsop) standard pinout tr = 48-pin thin small outline package (tsop) reverse pinout pbt = 63-ball fine pitch ball grid array package (fbga) speed option see product selector guide device revision boot code sector architecture t = top sector b = bottom sector device number/description mbm29lv320 32mega-bit (4 m 8-bit or 2 m 16-bit) cmos flash memory 3.0 v-only read, program, and erase valid combinations valid combinations mbm29lv320te/be 80 90 10 tn tr pbt valid combinations list configurations planned to be supported in volume for this device. consult the local fujitsu sales office to confirm availability of specific valid combinations and to check on newly released combinations.
mbm29lv320te/be 80/90/10 62 n package dimension (continued) 48-pin plastic tsop (i) (fpt-48p-m19) * resin protrusion. (each side: 0.15 (.006) max) 48-pin plastic tsop (i) (fpt-48p-m20) * resin protrusion. (each side: 0.15 (.006) max) C .003 +.001 C 0.08 +0.03 .007 0.17 "a" (stand off height) 0.10(.004) (mounting height) (.472 .008) 12.00 0.20 * * lead no. 48 25 24 1 (.004 .002) 0.10(.004) m 1.10 +0.10 C 0.05 +.004 C .002 .043 0.10 0.05 (.009 .002) 0.22 0.05 typ 0.50(.020) (.453) 11.50ref (.787 .008) 20.00 0.20 (.724 .008) 18.40 0.20 index 2001 fujitsu limited f48029s-c-4-5 c 0~8 ? 0.25(.010) 0.60 0.15 (.024 .006) details of "a" part dimensions in mm (inches) c 2000 fujitsu limited f48030s-3c-4 details of "a" part 0.15(.006) max 0.35(.014) max 0.15(.006) 0.25(.010) index "a" 18.40?.20 (.724?008) 20.00?.20 (.787?008) 19.00?.20 (.748?008) 0.50?.10 (.020?004) 0.15?.05 (.006?002) 11.50(.453)ref 0.50(.020) typ 0.20?.10 (.008?004) .043 ?002 +.004 ?.05 +0.10 1.10 m 0.10(.004) 1 24 25 48 lead no. * * 12.00?.20(.472?008) (mounting height) 0.10(.004) 0.10?.05 (.004?002) (stand off) mounting height dimensions in mm ( inches )
mbm29lv320te/be 80/90/10 63 (continued) 63-pin plastic fbga (bga-63p-m01) c 2001 fujitsu limited b63001s-c-2-2 11.00 0.10(.433 .004) .041 ?004 +.006 ?.10 +0.15 1.05 (mounting height) 1 2 3 4 5 6 7 8 a b c d e f g h 0.80(.031)typ (5.60(.220)) (5.60(.220)) index ball m 0.08(.003) 0.10(.004) index area 7.00 0.10 (.276 .004) (7.20(.283)) j k (63-?.18 .002) 63-?.45 0.05 ml (8.80(.346)) (4.00(.157)) 0.38 0.10 (.015 .004) (stand off) dimensions in mm (inches)
mbm29lv320te/be 80/90/10 fujitsu limited for further information please contact: japan fujitsu limited marketing division electronic devices shinjuku dai-ichi seimei bldg. 7-1, nishishinjuku 2-chome, shinjuku-ku, tokyo 163-0721, japan tel: +81-3-5322-3353 fax: +81-3-5322-3386 http://edevice.fujitsu.com/ north and south america fujitsu microelectronics america, inc. 3545 north first street, san jose, ca 95134-1804, u.s.a. tel: +1-408-922-9000 fax: +1-408-922-9179 customer response center mon. - fri.: 7 am - 5 pm (pst) tel: +1-800-866-8608 fax: +1-408-922-9179 http://www.fma.fujitsu.com/ europe fujitsu microelectronics europe gmbh am siebenstein 6-10, d-63303 dreieich-buchschlag, germany tel: +49-6103-690-0 fax: +49-6103-690-122 http://www.fme.fujitsu.com/ asia pacific fujitsu microelectronics asia pte. ltd. #05-08, 151 lorong chuan, new tech park, singapore 556741 tel: +65-281-0770 fax: +65-281-0220 http://www.fmal.fujitsu.com/ korea fujitsu microelectronics korea ltd. 1702 kosmo tower, 1002 daechi-dong, kangnam-gu,seoul 135-280 korea tel: +82-2-3484-7100 fax: +82-2-3484-7111 f0202 ? fujitsu limited printed in japan all rights reserved. the contents of this document are subject to change without notice. customers are advised to consult with fujitsu sales representatives before ordering. the information and circuit diagrams in this document are presented as examples of semiconductor device applications, and are not intended to be incorporated in devices for actual use. also, fujitsu is unable to assume responsibility for infringement of any patent rights or other rights of third parties arising from the use of this information or circuit diagrams. the products described in this document are designed, developed and manufactured as contemplated for general use, including without limitation, ordinary industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as contemplated (1) for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could have a serious effect to the public, and could lead directly to death, personal injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system), or (2) for use requiring extremely high reliability (i.e., submersible repeater and artificial satellite). please note that fujitsu will not be liable against you and/or any third party for any claims or damages arising in connection with above-mentioned uses of the products. any semiconductor devices have an inherent chance of failure. you must protect against injury, damage or loss from such failures by incorporating safety design measures into your facility and equipment such as redundancy, fire protection, and prevention of over-current levels and other abnormal operating conditions. if any products described in this document represent goods or technologies subject to certain restrictions on export under the foreign exchange and foreign trade law of japan, the prior authorization by japanese government will be required for export of those products from japan.

▲Up To Search▲

Price & Availability of MBM29LV320BE80TR

	To Download MBM29LV320BE80TR Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .